Skip to content

Conversation

@foskey51
Copy link

@foskey51 foskey51 commented Oct 3, 2025

Please answer these questions before submitting a pull request, or your PR will get closed.

Why submit this pull request?

  • Bugfix
  • New feature provided
  • Improve performance
  • Backport patches

What changes will this PR take into?

This PR addresses how sensitive fields are handled in Settings and Secrets by changing their input type to password and introducing a toggle to switch between masked and plain-text views.

Settings:

  • Admin Key

Behaviour:

  • Masked by default
  • Toggle icon to switch b/w text view and masked view

Secrets (page):

  • Secret Manager (section):
    • Vault
      • Token
    • AWS
      • Secret Access Key
      • Session Token
    • GCP
      • Private Key

Behaviour:

  • Masked by default
  • Toggle icon to switch b/w text view and masked view (available in edit mode only)

Related issues

fix/resolve #3218

Checklist:

  • Did you explain what problem does this PR solve? Or what new features have been added?
  • Have you added corresponding test cases?
  • Have you modified the corresponding document?
  • Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Change sensitive fields (admin keys, vault tokens) from input type text to password (default) with a toggle to show/hide values
Copy link
Contributor

@Baoyuantop Baoyuantop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to add a simple test for this switch.

@Baoyuantop Baoyuantop requested a review from SkyeYoung October 8, 2025 02:12
@foskey51 foskey51 requested a review from Baoyuantop October 10, 2025 05:47
@Baoyuantop
Copy link
Contributor

Hi @foskey51, can you add a simple test for this modification? You can refer to the existing e2e testing process.

Gurleen-kansray and others added 5 commits October 18, 2025 15:31
The Bitnami etcd image (bitnami/etcd:3.5) is deprecated and no longer available in Docker Hub. 
Updated the reference in e2e/server/docker-compose.common.yml to use bitnamilegacy/etcd:3.5 instead. 
This resolves the dev container build failure mentioned in issue #3220.
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3 to 4.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@v3...v4)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-version: '4'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v6)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@foskey51 foskey51 closed this Oct 18, 2025
@foskey51 foskey51 deleted the feat/mask-sensitive-fields branch October 18, 2025 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Sensitive keys and tokens are visible in the APISIX Dashboard

4 participants